chore: add Greptile code review configuration by elkaix · Pull Request #61 · PyModel/pythinker-code

elkaix · 2026-08-12T02:33:58Z

Related Issue

No issue — repository tooling configuration, no product behavior change. Problem explained below.

Problem

Greptile code review is enabled for this repository but runs unconfigured: default strictness, all comment types (including style/info nits), no repo-specific rules, and no pointers to the AGENTS.md contributor guides. This produces noisy reviews that overlap with CodeRabbit and miss repo-specific conventions.

What changed

Add a root .greptile/ configuration folder (the current recommended format; supersedes legacy greptile.json):

config.json — strictness 2, logic + syntax comments only, re-review on PR updates, review only PRs targeting main, skip WIP / DO NOT REVIEW titles, ignore patterns mirrored from .coderabbit.yaml, and five scoped structured rules with stable IDs (type-weakening, flake.nix workspace sync, vacuous test assertions, TUI reactivity, changeset requirement) so nested configs can disable them later.
rules.md — prose conventions distilled from AGENTS.md: TypeScript idioms, architecture boundaries, and hygiene rules.
files.json — points the reviewer at the six AGENTS.md files, each scoped to its directory tree.

Settings cascade, so packages can add their own .greptile/ overrides later without touching the root config. Docs: https://www.greptile.com/docs/code-review/greptile-config

Checklist

I have read the CONTRIBUTING document.
I have linked a related issue, or explained the problem above.
I have added tests that prove my feature works. — N/A: review-bot configuration only, no code paths to test.
Ran gen-changesets skill, or this PR needs no changeset. — No changeset: nothing enters any package output.
Ran gen-docs skill, or this PR needs no doc update. — No user-facing product change.

Summary by CodeRabbit

Documentation
- Added repository guidance for automated code reviews.
- Documented TypeScript conventions, architectural boundaries, dependency and feature-flag constraints, and project hygiene requirements.
- Added scoped guidance for CLI, web, server, end-to-end testing, service-layer, and documentation areas.
- Configured review standards covering type safety, workspace synchronization, test effectiveness, interface responsiveness, and required release documentation.

coderabbitai · 2026-08-12T02:34:19Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e59b2f1d-0395-41a9-ba9f-71ed55b5e322

📥 Commits

Reviewing files that changed from the base of the PR and between e7ef634 and 0cd20ee.

📒 Files selected for processing (2)

.greptile/config.json
.greptile/files.json

🚧 Files skipped from review as they are similar to previous changes (2)

.greptile/files.json
.greptile/config.json

📝 Walkthrough

Walkthrough

Added Greptile configuration, scoped guidance registration, and repository review rules. The configuration defines review triggers, exclusions, contributor instructions, and five scoped checks. The rules document covers TypeScript, architecture, testing, feature flags, dependencies, compatibility, and repository hygiene.

Changes

Greptile review setup

Layer / File(s)	Summary
Review policy and repository guidance `.greptile/config.json`, `.greptile/files.json`, `.greptile/rules.md`	Configures review behavior and triggers, registers scoped `AGENTS.md` guidance, and documents repository rules for code structure, dependencies, tests, feature flags, compatibility, and internal identifiers.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title uses the required chore prefix, imperative wording, is 45 characters long, and accurately describes the configuration changes.
Description check	✅ Passed	The description includes all required sections and explains the no-issue, no-tests, no-changeset, and no-doc-update decisions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{Comment @coderabbitai help to get the list of available commands.}

pkg-pr-new · 2026-08-12T02:35:45Z

pnpm dlx https://pkg.pr.new/@pythoughts/pythinker-code@0cd20ee

npx https://pkg.pr.new/@pythoughts/pythinker-code@0cd20ee

commit: 0cd20ee

greptile-apps · 2026-08-12T02:38:11Z

Greptile Summary

The review configuration now includes the agent-core service guide for service-layer changes. Both JSON configuration files parse successfully, and the guide is registered once with the intended scope.

Confidence Score: 5/5

No blocking failure remains.

No accepted blocking findings remain.

T-Rex Logs

What T-Rex did

Ran a focused Greptile configuration validation script against .greptile/files.json and .greptile/config.json to verify that the AGENTS.md service guide is registered for the expected files.
Verified that packages/agent-core/src/services/AGENTS.md exists, appears once in .greptile/files.json, and has scope packages/agent-core/src/services/**; the validation script reported success with all five assertions passing.

_{Ran code and verified through T-Rex}

_{Reviews (2): Last reviewed commit: "chore: address review feedback on Grepti..." | Re-trigger Greptile}

coderabbitai

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.greptile/config.json:
- Around line 34-36: Update the changeset-required rule to match the repository
policy: require a changeset for PRs affecting release artifacts, code, behavior,
or public APIs, while allowing docs-only, test-only, and CI-only changes to skip
it; preserve the existing version guidance.
- Line 8: Update the `instructions` field in `.greptile/config.json` to
distinguish `packages/node-sdk` as the public SDK from the internal engine
packages (`packages/agent-core`, `kosong`, `kaos`, `oauth`, and `telemetry`),
replacing the inaccurate claim that all `packages/*` are published libraries.
- Line 3: Update the commentTypes configuration to include the style and info
categories alongside logic and syntax, ensuring custom-rule hygiene and
convention feedback is not filtered out.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 59ae678f-1d11-4704-8600-c55fd979a435

📥 Commits

Reviewing files that changed from the base of the PR and between 45887dc and e7ef634.

📒 Files selected for processing (3)

.greptile/config.json
.greptile/files.json
.greptile/rules.md

chore: add Greptile code review configuration

e7ef634

greptile-apps Bot reviewed Aug 12, 2026

View reviewed changes

Comment thread .greptile/files.json

coderabbitai Bot reviewed Aug 12, 2026

View reviewed changes

Comment thread .greptile/config.json Outdated

Comment thread .greptile/config.json Outdated

Comment thread .greptile/config.json

chore: address review feedback on Greptile configuration

0cd20ee

elkaix merged commit 4c41c24 into main Aug 12, 2026
13 checks passed

elkaix deleted the chore/greptile-config branch August 12, 2026 02:44

Navigation Menu

Uh oh!

chore: add Greptile code review configuration - #61

chore: add Greptile code review configuration#61
elkaix merged 2 commits into
mainfrom
chore/greptile-config

elkaix commented Aug 12, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Aug 12, 2026 •

edited

Loading

Walkthrough

Changes

Uh oh!

pkg-pr-new Bot commented Aug 12, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot commented Aug 12, 2026 •

edited

Loading

T-Rex Logs

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

elkaix commented Aug 12, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Related Issue

Problem

What changed

Checklist

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Aug 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

pkg-pr-new Bot commented Aug 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

greptile-apps Bot commented Aug 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 5/5

T-Rex Logs

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

elkaix commented Aug 12, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Aug 12, 2026 •

edited

Loading

pkg-pr-new Bot commented Aug 12, 2026 •

edited

Loading

greptile-apps Bot commented Aug 12, 2026 •

edited

Loading